NetApp
Vserver : Policies > QoS Policies : Understanding QoS Policies : Rules for assigning storage objects to policy groups

Rules for assigning storage objects to policy groups
You should be aware of rules that dictate how you can assign storage objects to Storage QoS policy groups.
Storage objects and policy groups must belong to the same Vserver
A storage object must be contained by the Vserver to which the policy group belongs. You specify the Vserver to which the policy group belongs when you create the policy group. Multiple policy groups can belong to the same Vserver.
In the following illustration, the policy group pg1 belongs to Vserver vs1. You cannot assign volumes vol2 or vol3 to policy group pg1 because those volumes are contained by a different Vserver.
Nested storage objects cannot belong to policy groups
You cannot assign a storage object to a policy group if its containing object or its child objects belong to a policy group. The following table lists the restrictions.
In the following illustration, the Vserver vs3 is assigned to policy group pg2. You cannot assign volumes vol4 or vol5 to a policy group because an object in the storage hierarchy (Vserver vs3) is assigned to a policy group.
Some types of volumes not supported with Storage QoS
You can assign FlexVol volumes to policy groups. Infinite Volumes are not supported with Storage QoS.
The following FlexVol volume variations are not supported with Storage QoS:
•
•
•
•
Note: You can assign the origin volume to a policy group, which controls the origin volume and its FlexCache volumes.


Was this topic helpful? Send comments to NetApp.